Distributed network node operation system based on operation control unit

ABSTRACT

A distributed network node operation system based on an operation control unit. The operation system operates on a network node and interacts with a data link layer, and includes: an application interface unit, a network information management unit, a file unit, a task scheduling unit and a device drive management unit. The application interface unit packages the services provided by the file unit, the task scheduling unit and the network information management unit into an interface for interacting with the protocol stack management unit; the network information management unit interacts with the data link layer to perform link scheduling for transmitting information and updating node data; the file unit manages and stores file information; the task scheduling unit manages hardware resources; the device drive management unit manages underlying device application drives, and invokes different protocol stack library functions through different application drives.

CROSS REFERENCE TO RELATED APPLICATIONS

The present application is a continuation of international applicationno. PCT/CN2016/071201, filed on Jan. 18, 2016, which claims priority toChina Patent Application no. 2015103335779, filed on Jun. 15, 2015, bothof which are hereby incorporated by reference in their entireties.

TECHNICAL FIELD

The present invention application relates to a distributed network nodeoperation system applied to an Internet of Things, and in particular, toa distributed network node operation system based on an operationcontrol unit.

BACKGROUND ART

Internet of Things is network for realizing informationization, remotemanagement control and intelligentization by linking sensors,controllers, machines, persons and things together in a new mannerthrough communication technology such as a local network or Internet toform links between people and things and between things. With the rapiddevelopment of Internet of Things technology, more and more articles arenetworked. However, intercommunication can hardly be achieved due todifferent standards of information systems built in different regions indifferent stages, and the so-called “information isolated islands” areformed. The user needs a uniform platform in which a plurality ofnetworks and a plurality of protocols are compatible to realizeintercommunication.

As one way for implementing the Internet of Things, a Wireless SensorNetwork (WSN) is a wireless network consisting of a large number ofstatic or mobile sensors in a self-organizing and multi-hop manner tocollaboratively sense, acquire, process and transmit information ofobjects sensed in a geographic region covered by the network and finallysend this information to the owner of the network.

A wireless sensor network is generally equipped with an operationsystem, and the operation system of the wireless sensor network isintended to provide a good user interface for the user. An operationsystem with good performance can allow optimal and reasonable resourceallocation, and stable and reliable work during the operating process ofthe whole system.

The main current wireless sensor network operation systems are as below:

(1) TinyOS, an open-source embedded operation system developed byUniversity of California, Berkeley, which can rapidly implement variousapplications based on the architecture mode of parts, and is currentlymainly used in the field of wireless sensor network.

(2) MiniOS, a multi-task operation system based on sensor network nodehardware environment, which provides an easy universal developmentplatform for users;

(3) MantisOS, a micro operation system facing sensor networks developedby University of Colorado, which provides multi-frequency communicationand suitable for multi-task sensor nodes.

Among these, the most popular one is TinyOS, and most of the researchesand developments in sensor network application use the software systemdesign of TinyOS. However, TinyOS adopts a compromised method betweenfunctions and hardware restriction. Due to the limit on memory space,TinyOS uses the first-in-first-out scheduling strategy for taskmanagement, which can hardly meet the application requirement of theincreasingly complicated sensor systems. With the development of microcontrollers, the processing ability and storage capacity are graduallyincreased, and a single-task operation system cannot make full use ofsystem resources any more for meeting complicated user demands.

Moreover, an embedded operation system widely used in the Internet ofThings system generally includes a underlying drive software relatedwith hardware, system kernel, device drive interface, communicationprotocol, graphic interface, standardized browser, etc. The embeddedoperation system is responsible for allocation of all software andhardware resources, task scheduling of the embedded system, andcontrolling and coordinating concurrent activities. The currently mainembedded operation systems are as blow:

(1) Windows CE: it is an open and scalable 32-bit embedded operationsystem developed by Microsoft, and a typical embedded system based onWindows CE is generally designed for a certain specific use, and workswithout being online. It requires the operation system to be used tohave small size and have an in-built response function for interruption.

(2) VxWorks operation system: it is an embedded real-time operationsystem designed and developed by WindRiver. VxWorks has a cuttablemicrokernel structure;

highly efficient task management; flexible inter-task communication;interruption processing at microsecond speed; supports POSIX 1003. 1 breal-time expansion standard; supports multiple physical mediums andstandard, complete TCP/IP network protocols, etc. however, the costs fordeveloping and maintaining the software are too high, and the number ofhardware that can be supported is limited.

(3) μC/OS

II: it is a preemptive multi-task real-time operation system based onpriority, and is specially designed for embedded application, and it canbe used in 8-bit, 16-bit and 32-bit single chip microcomputers ordigital signal processors. SinceμC/OS

II is only a real-time kernel, it means that unlike other real-timesystems, it can only provide the users with some API function interface,and there is still a lot of work to be done by the users themselves.

From the view of the existing embedded operation systems, most of theembedded operations systems face the control process, and emphasize thecontrol and scheduling for system resources, but the space for secondarydevelopment and improvement for users is very small, and thus cannotmeet the requirement for the development of the Internet of Things.

The disclosure of the above background art is only for assisting theunderstanding of the concept and technical solution of the presentinvention application, and does not necessarily belong to the prior artof the present invention application. The above background art shall notbe used to evaluate the novelty and inventiveness of the presentapplication without any explicit evidence showing that the above contenthas been disclosed before the filing date of the present inventionapplication.

SUMMARY OF THE INVENTION

The (main) object of the present invention application lies in that adistributed network node operation provided by the present patent facesa communication without changing the architecture of the networkprotocol macroscopically, and is transparent to the upper-layerapplications; plentiful user interfaces are provided for facilitatingsecondary development and improvement.

Compared with the prior art, the beneficial effects of the presentinvention application include: the distributed network node operationsystem based on an operation control unit according to the presentinvention can be applied to underlying devices of differentcommunication modes and networking modes, the corresponding applicationdrives of these devices may be invoked, and library functions ofdifferent protocol stacks may be invoked for routing and applicationmanagement of the network, thereby making a plurality of communicationmodes and protocols compatible. Therefore, the operation system of thepresent application is compatible with a plurality of networks and aplurality of protocols, thus realizing intercommunication.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 illustrates the system of a distributed network node operationsystem based on an operation control unit according to the presentinvention.

FIG. 2 illustrates a block chain according to the present invention.

FIG. 3 illustrates the system of a distributed network node operationsystem based on an operation control unit according to another exampleof the present invention.

FIG. 4 is a flowchart of a method for active information push by anetwork node according to the present invention.

FIG. 5 is a flowchart of data update in the method for activeinformation push by a network node according to the present invention.

SPECIFIC EMBODIMENTS

The present invention application will be further described below withreference to the drawings in conjunction with specific examples. Itshould be noted that the following description is only for illustration,and is not intended to limit the scope and utilization of the presentinvention application.

Non-restrictive and non-exclusive examples will be described withreference to the following drawings, in which the same reference signsindicate the same parts, unless specifically explained otherwise.

A person skilled in the art shall appreciate that various modificationcan be made to the description, and thus the examples are only used todescribe one or more specific embodiments.

FIG. 1 illustrates a distributed network node operation system based onan operation control unit according to the present invention implantedon distributed network nodes. As shown in FIG. 1, the distributednetwork node operation system based on an operation control unitaccording to the information of the present invention is located betweenan upper-layer application and an underlying device. The upper-layerapplication is located above the operation system, and it is a set ofapplications providing a certain particular service for the user.

Taking the Internet of Things as an example, each node may represent oneterminal in the Internet of Things. For example, in an Internet ofvehicles, each node may represent a vehicle. In an Internet of Thingsconsisting of a plurality of wearable smart devices, each node mayrepresent one wearable smart device, such as smart watch or smartglasses.

As shown in FIG. 1, the distributed network node operation systemaccording to the present invention directly interacts with a data linklayer, and thus can directly perform link scheduling with a networklayer through the data link layer to transmit node information andupdate the data of the node or between nodes. The distributed networknode operation system according to the present invention may be directlylocated in the data link layer, or be embedded in the data link layer,to achieve direct interaction with the data link layer.

The distributed network node operation system based on an operationcontrol unit according to the present invention includes: an applicationinterface unit, a network information management unit, a file unit, atask scheduling unit and a device drive management unit.

The network information management unit interacts with the data linklayer to perform link scheduling for transmitting information andupdating node data. Specifically, according to an example of the presentinvention, the network information management unit is configured to,when the data acquired by the acquisition nodes are changed, control theacquisition nodes to plan a push path according to a routing table,encapsulate the data acquired this time, end information abstract in ablock chain and the push path, and actively push the encapsulatedinformation to a first neighbor node where network communication canreach, and write the data acquired this time into the end of the blockchain of the acquisition nodes, and finally send the encapsulatedinformation to a cloud. The network information management unit is incharge of management of network information. According to an example ofthe present invention, it may include a data push sub-unit which isresponsible for automotive push of information between nodes and a dataupdate sub-unit which is responsible for update of data between thenodes.

In an example, information abstract includes time stamps, a number ofacquisition nodes and tags of the acquisition nodes.

In the present invention, the first neighbor node refers to the node inthe one-hop communication range of the acquisition node. Theincorporation herein means that when the neighbor node receives two ormore pieces of information with the same time stamp but sent bydifferent acquisition node tags, the neighbor node combines thisinformation into a format of time stamp, the number of acquisitionnodes, the tags of the acquisition nodes, data, the tags of theacquisition nodes data . . . Wherein, the number of the colleting nodesis determined according to the number of the tags of the acquisitionnodes, each tag of acquisition node is followed immediately by its data,and the order of the tags of the acquisition nodes may be agreed inadvance, for example in an ascending order, and the like.

After the first neighbor node receives the encapsulated informationshared by the acquisition node, the network information management unitincorporates the time stamp of this time, the tags of the acquisitionnode and the data in the encapsulated information into the block chainin an order according to the time stamps; meanwhile it actively pushesthe received encapsulated information to the second neighbor node. Insuch a way, the second neighbor node can actively push the encapsulatedinformation to the third neighbor node. The number of times of activepush may be determined according to the specific condition of thenetwork.

The application interface unit is a set of application interfaces forencapsulating the services provided by the file unit, the taskmanagement unit and the information management unit into a programmaticinterface available to the upper-layer applications and providing aninterface for interacting with the library functions of the protocolstack. The application interface unit converts the services provided bythe file unit, the task scheduling unit and the network informationmanagement unit to a programmatic interface available to the upper-layerapplications.

The file unit is responsible for managing and storing file information,organizing and allocating the space of the file storage device, andstoring files and protecting and searching the stored files.

The task scheduling unit is responsible for managing the hardwareresources. According to an example of the present invention, the e taskscheduling unit includes processor management, memory management and IO(input and output devices) management. A processor management sub-unitis responsible for allocating and controlling processors. A memorymanagement sub-unit is responsible for allocation and recycle of memory.An IO device management sub-unit is responsible for allocation andmanipulation of IO devices.

The device drive management unit is responsible for managing theunderlying application drives, and invoking different protocol stacklibrary functions through different application drives, thus making aplurality of communication modes and protocols compatible.

The application interface unit of the distributed network node operationsystem is also interfaced with a protocol stack management unit.

The protocol stack management unit encapsulates a set of libraryfunctions of the protocol stacks of different network protocols. Theapplication interface unit further provides an interface for interactingwith the library functions of the protocol stacks. The protocols includebut not limited to WiFi, ZigBee, Bluetooth, etc. The present inventionapplication enables the protocol stack to encapsulate library functions,and the operation system provides a scheduling interface for theprotocol stack. The operation system supports underlying devices ofdifferent communication modes and networking modes, and can invoke theapplication drives of these devices. The library functions of differentprotocol stacks are invoked for routing and application management ofthe network, making a plurality of communication modes and protocolscompatible. This ensures universality of the network. According to anexample of the present invention, the protocol stack management unit maybe located in a MAC layer.

According to an example of the present invention, the data of thenetwork node is stored in a form of block chain table, as shown in FIG.2.

Information abstracts contains time stamp, the number of acquisitionnodes and tags of the acquisition nodes.

The first neighbor node refers to the node within one-hop communicationrange of the acquisition node

Push Time Number of Tags of Time Tags of Data path stamp at acquisitionacquisition stamp of acquisition the end of nodes at nodes at this timenodes the block the end the end chain

This format is only illustration of the network layer. Please see thecorresponding network protocol for other parts such as check. Sinceother parts of the data packet are not within the protection scope ofthe present invention, they are not listed herein.

As shown in FIG. 2, a block chain is a chain table structure for storinghistory data, and achieves the purpose of recording by recording time,the number of acquisition nodes, the tags of the acquisition nodes anddata. Wherein, a block chain includes a plurality of the aboveinformation abstracts.

Different blocks have different sizes, because there may be severalnodes acquiring data at a certain time point, and the number of theacquisition nodes is required to record the number of nodes with changeddata at this moment.

Preferably, the information abstracts of the block chain table aresequenced in an order from old to new according to the time stamps.

According to a specific example, when the data of the network node arestored in the manner of block chain table, after the network nodereceives the information, the received information tag is compared withthe node tag in the existing block chain table. If there are the samenode tags, a new data block is used to replace the old one in an orderaccording to the time stamps; if there is no same node tag, a new datablock is entirely incorporated into the end of the block chain table.

FIG. 3 illustrates a specific example of the distributed network nodeoperation system including an operation control unit implemented on eachnetwork node according to the present invention.

As shown in FIG. 3, the distributed network node operation system basedon an operation control unit according to the present invention isimplemented between an underlying device and an upper-layer application.In particular, the data link layer may be divided into a logic linksub-layer (LLC layer) and a media access control sub-layer (MAC layer).According to an example of the present invention, the distributednetwork node operation system according to the present invention may belocated between the logic link sub-layer (LLC layer) and the mediaaccess control sub-layer (MAC layer). According to another example ofthe present invention, the distributed network node operation systemaccording to the present invention may also be incorporated with thelogic link sub-layer (LLC layer) and the media access control sub-layer(MAC layer).

Since the distributed network node operation system according to thepresent invention works between the data link layer and the physicallayer, the architecture of the network protocol is not changedmacroscopically and is transparent to the upper-layer applications;plentiful user interfaces are provided for facilitating secondarydevelopment and improvement.

In the present example, the network information management unit isresponsible for managing the data frames transmitted between the datalink layer and the physical layer, and selectively storing the dataframes according to the corresponding application requirements.

In this example, the network information management unit selectivelydata frames according to the corresponding application requirements, andthe data frames are stored in the file unit. The file unit distinguishesdifferent data versions by recording a particular tag. The so-calledparticular tag includes but not limited to time stamp, event drive.

In this example, the hardware resource management unit is alsoresponsible for scheduling various tasks in the distributed network nodeoperation system. The scheduling algorithm includes real-time preemptionscheduling mode of event triggering. Due to direct interaction with thedata link layer, the distributed network operation system of the presentpatent can achieve real-time preemption scheduling mode based on eventtriggering. When the data frames in the data link layer need to betransmitted to the physical layer, or the bit streams received by thephysical layer need to be transmitted to the data link layer, tasks ofcorresponding priorities will be established in the network informationmanagement unit and uniformly scheduled by the task scheduling unit toensure that respond can be made to the essential tasks immediately. Asfor the established tasks of different priorities, in addition totransmission of data, other processing may also be made to the dataaccording to the actual application requirements so as to facilitatesecondary development and application.

The device drive management unit is responsible for managing applicationdrives of the underlying devices, selecting the correspondingapplication drives according to different underlying devices, andperforming the corresponding initiation. By invoking differentunderlying drives, different underlying hardware devices are supported.

In this example, by means of device drive management and protocol stackmanagement, a plurality of networking modes, including but not limitedto star network, mesh network, loop network and other network topologystructures, can be supported; a plurality of wireless communicationprotocols including but not limited to WiFi, ZigBee and Bluetooth canalso be supported through the LLC layer and the MAC layer. Depending onthe underlying devices of different communication modes and networkingmodes, the corresponding application drives of these devices may beinvoked, and library functions of different protocol stacks may beinvoked for routing and application management of the network, therebymaking a plurality of communication modes and protocols compatible.Therefore, the operation system of the present application is compatiblewith a plurality of networks and a plurality of protocols, thusrealizing intercommunication.

FIG. 4 is a flowchart of a method for active information push by anetwork node according to the present invention. The above nodeoperation system operates on the network node, and the operation systemdirectly interacts with the data link layer. The operation systemincludes: an application interface unit, a network informationmanagement unit, a file unit, a task scheduling unit and a device drivemanagement unit.

As shown in FIG. 4, in another example, the method for activeinformation push includes the following steps:

Step one: a network node accesses a network;

Step two: the node communicates with the cloud, and requests forupdating routing; communicating with the cloud according to the presentinvention means receiving data from other nodes in the network. Sincethe node operation system of the present invention operates each networknode, and when the data of the node are changed, data may be activelypushed to other nodes in an event driven manner.

Step three: receive the updated routing from the cloud;

Step four: the node acquires data;

Step five: detect whether the acquired data are chanted or not, if yes,proceed to step six; otherwise, proceed to step eight;

Step six: the node plans a push path according to the routing by meansof the network information management unit, and after encapsulation, itpushes the information to the reachable node and adds the information tothe block chain; the “reachable node ” here may refer to the firstneighbor node;

Step seven: the node sends data to the cloud, i.e., actively push thedata to other nodes;

Step eight: the node checks whether there are new data in the cachedreceived data, and if there is no new data, return to step four; ifthere are new data, proceed to step nine;

Step nine: the node incorporates the newly received information into theblock chain;

Step ten: the received information is continually pushed to other nodesaccording to the routing plan, return to step four.

After the encapsulated information is received the encapsulatedinformation are distinguished according to information abstracts. Alldata have copies at the cloud, and are stored in the manner of blockchain and are distinguished according to information abstracts. Datapush is performed in a manner using change of acquired data as the eventdriving, i.e., once the acquired data are changed, the node has toperform one data push.

During the process of active data push, if the time stamp at the end ofthe block chain, a number of end acquisition nodes and tags of endacquisition nodes in the information received by the neighbor node arenot consistent with a block in a block chain of a neighbor node, thenthe neighbor node sends to the cloud a request containing informationabstracts for distinguishing information versions; after receiving therequest, the cloud sends a block of a corresponding version according tothe information abstracts and all blocks after the block to the neighbornode.

When the neighbor node receives more than two information versions withthe same information abstract and these information versions havedifferent contents, the neighbor node sends to the cloud a requestcontaining information abstracts for distinguishing data versions; afterreceiving the request, the cloud sends a block of a correspondingversion according to the information abstracts and all blocks after theblock to the neighbor node.

FIG. 5 is a flowchart of data update in the method for activeinformation push by a network node according to the present invention,as shown in FIG. 5.

In another example, the process of active push further involves thefollowing data update operation:

Step one: a neighbor node receives information;

Step two: detect whether the time stamps, the number of end nodes andtags of end acquisition nodes in the information received by the nodeare not consistent with a block in a block chain of a neighbor node, ifyes, proceed to step three; otherwise, proceed to step six;

Step three: detects whether there is information with the same timestamp this time and different acquisition node tags, if yes, proceed tostep four; otherwise, proceed to step five;

Step four: perform incorporation processing, i.e., combines thisinformation into a format of time stamp, the number of acquisitionnodes, the tags of the acquisition nodes, data, the tags of theacquisition nodes data . . . Wherein, the number of the acquisitionnodes is determined according to the number of the tags of theacquisition nodes, each tag of acquisition node is followed immediatelyby its data;

Step five: detect whether there is information with the same time stampthis time, same number of acquisition nodes and same tags of acquisitionnodes but with different data contents, if yes, proceed to step six;otherwise, proceed to step eight;

Step six: the neighbor node sends to the cloud a request includinginformation abstracts for distinguishing data versions (please note thatfor hopping from step two, information abstracts refers to time stamp atthe end of the block chain, the number of end acquisition nodes and tagsof end acquisition nodes; as for hopping from step five, informationabstracts refers to time stamp of this time, the number of acquisitionnodes and tags of the acquisition nodes);

Step seven: the cloud sends the corresponding blocks as needed;

Step eight: the neighbor node adds the information to its own blockchain. Data update means distinguishing different data versions by wayof recording information of each node such as application data andeffective time through managing block chains. The so-called specific tagincludes but not limited to time stamp and event driving.

With the present invention application, a highly efficient, reliableuniversal wireless network may be formed. Any node can read the datapushed and updated by each node in the network through this softwarewithin the definition range reachable for the network communication, andthe definition of these data that can be read may be maintained by thenetwork information management function.

Though the exemplary examples of the present invention application havebeen described and depicted, a person skilled in the art shallappreciate that various modifications and replacements made by made tothe present application without departing from the spirit of the presentpatent. Moreover, many changes may be made to adapt particular cases tothe teaching of the present invention without departing from the coreconcept of the present invention application. Therefore, the presentinvention application is not limited to the specific examples disclosedherein, and the present invention application may further include allexamples and other equivalents within the scope of the present inventionapplication.

What is claimed is:
 1. A distributed network node operation system basedon an operation control unit, the operation system operating on thenetwork node and directly interacting with a data link layer, theoperation system comprising: an application interface unit, a networkinformation management unit, a file unit, a task scheduling unit and adevice drive management unit, wherein, the application interface unit isa set of application interfaces, and packages services provided by thefile unit, the task scheduling unit and the network informationmanagement unit into an interface for interacting with the protocolstack management unit; the network information management unit isconfigured to interact with the data link layer to perform linkscheduling for transmitting information and updating node data; the fileunit is configured to manage and store file information, organize andallocate space of a file storage device, and is responsible for filestorage and protecting and searching stored files; the task schedulingunit is configured to manage hardware resources; the device drivemanagement unit is configured to manage underlying device applicationdrives, and to invoke different protocol stack library functions throughdifferent application drives, thus making a plurality of communicationmodes and protocols compatible.
 2. The distributed network nodeoperation system according to claim 1, wherein, the applicationinterface unit is configured to interface with a protocol stackmanagement unit located in MAC, and the protocol stack management unitis configured to encapsulate a set of library functions of protocolstacks of different network protocols.
 3. The distributed network nodeoperation system according to claim 1, wherein, the operation system isincorporated with a LLC layer and a MAC layer.
 4. The distributednetwork node operation system according to claim 1, wherein, the networkinformation management unit comprises a data push sub-unit which isresponsible for automotive push of information between nodes and a dataupdate sub-unit which is responsible for update of data between thenodes.
 5. The distributed network node operation system according toclaim 1, wherein, data of the network node are stored in a manner of ablock chain table.
 6. The distributed network node operation systemaccording to claim 5, wherein, the block chain table comprises aplurality of information abstracts, including time stamps, a number ofacquisition nodes and tags of the acquisition nodes.
 7. The distributednetwork node operation system according to claim 6, wherein, the networkinformation management unit is configured to, when the data acquired bythe acquisition nodes are changed, control the acquisition nodes to plana push path according to a routing table, encapsulate the data acquiredthis time, end information abstract in a block chain and the push path,and actively push the encapsulated information to a first neighbor nodewhere network communication can reach, and write the data acquired thistime into the end of the block chain of the acquisition nodes, andfinally send the encapsulated information to a cloud.
 8. The distributednetwork node operation system according to claim 6, wherein, after aneighbor node receives the encapsulated information shared by theacquisition nodes, the network information management unit incorporatesthe time stamp of this time, the tags of the acquisition nodes and thedata in the encapsulated information into the block chain in an orderaccording to the time stamps; meanwhile actively pushes the receivedencapsulated information to another neighbor node according to the pushpath.
 9. The distributed network node operation system according toclaim 1, wherein, the task scheduling unit comprises a processormanagement sub-unit responsible for allocating and controllingprocessors, a memory management sub-unit responsible for allocation andrecycle of memory, and an IO (input and output devices) devicemanagement sub-unit responsible for allocation and manipulation of IOdevices.
 10. A method for a network node actively pushing informationbased on event driving, the network node operates an operation systemwhich directly interacts with a data link layer, the operation systemcomprising: an application interface unit, a network informationmanagement unit, a file unit, a task scheduling unit and a device drivemanagement unit, the method comprising the following steps of: a)detecting whether data acquired by the node are changed; b) when thedata acquired by the node are changed, the acquisition node planning apush path according to a routing table through the network informationmanagement unit, and actively pushing data information to a firstneighbor node where network communication can reach; c) the nodeupdating the data acquired this time to the file unit through thenetwork information management unit.
 11. The method for actively pushinginformation according to claim 10, wherein, the active push of the datainformation is conducted after the data acquired this time, endinformation abstract in a block chain and the push path areencapsulated.
 12. The method for actively pushing information accordingto claim 11, further comprising the step of: after the first neighbornode receives the encapsulated information, incorporating the time stampof this time, a tag of the acquisition node and the data in theencapsulated information into the block chain in an order according tothe time stamps; meanwhile actively pushing the received encapsulatedinformation to a second neighbor node according to the push path. 13.The method for actively pushing information according to claim 10,further comprising the step of: after a new node is added to thenetwork, sending an update routing to a network-wide updated routingtable.
 14. The method for actively pushing information according toclaim 11, wherein, after receiving the encapsulated data, the clouddistinguishes the encapsulated data according to information abstracts.15. The method for actively pushing information according to claim 12,wherein, if the time stamp at the end of the block chain, a number ofend acquisition nodes and tags of end acquisition nodes in theinformation received by the node are not consistent with a block in ablock chain of a neighbor node, then the node sends to the cloud arequest containing information abstracts for distinguishing informationversions; after receiving the request, the cloud sends a block of acorresponding version according to the information abstracts and allblocks after the block to the node.
 16. The method for actively pushinginformation according to claim 15, wherein, when the node receives morethan two information versions with the same information abstract andthese information versions have different contents, the node sends tothe cloud a request containing information abstracts for distinguishingdata versions; after receiving the request, the cloud sends a block of acorresponding version according to the information abstracts and allblocks after the block to the node.
 17. The method for actively pushinginformation according to claim 10, wherein, the network informationmanagement unit converts an information push service provided by itselfto an interface available to an upper-layer application program throughthe application interface unit.
 18. The method for actively pushinginformation according to claim 17, wherein, the application interfaceunit invokes a protocol stack management unit in a MAC layer to invokedifferent network protocols, so as to support information push ofunderlying devices of different communication modes and networkingmodes.